Skip to content

[Event Grid] Add Control Plane API Version 2025-04-01-preview#33889

Merged
JoshLove-msft merged 19 commits intoAzure:mainfrom
bbi2015:users/adebnath/eventgrid
May 22, 2025
Merged

[Event Grid] Add Control Plane API Version 2025-04-01-preview#33889
JoshLove-msft merged 19 commits intoAzure:mainfrom
bbi2015:users/adebnath/eventgrid

Conversation

@bbi2015
Copy link
Copy Markdown
Member

@bbi2015 bbi2015 commented Apr 11, 2025

ARM (Control Plane) API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

spec_pr_review_workflow_diagram

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

  • New resource provider.
  • New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
  • Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
  • Update existing version to fix OpenAPI spec quality issues in S360.
  • Convert existing OpenAPI spec to TypeSpec spec (do not combine this with implementing changes for a new API version).
  • Other, please clarify:
    • edit this with your clarification

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

  • I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
  • I have reviewed following Resource Provider guidelines, including
    ARM resource provider contract and
    REST guidelines (estimated time: 4 hours).
    I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

  • First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
  • If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
  • To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
  • For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
    and https://aka.ms/ci-fix.
  • For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
  • If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
    This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
  • If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app bot commented Apr 11, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

@openapi-pipeline-app
Copy link
Copy Markdown

openapi-pipeline-app bot commented Apr 11, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@bbi2015 bbi2015 requested a review from a-hamad April 11, 2025 08:30
@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Apr 11, 2025
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 11, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger Microsoft.EventGrid
JavaScript @azure/arm-eventgrid
Java com.azure.resourcemanager:azure-resourcemanager-eventgrid
C# Azure.ResourceManager.EventGrid
Go sdk/resourcemanager/eventgrid/armeventgrid

@razvanbadea-msft
Copy link
Copy Markdown
Member

    "userAssignedIdentity": {

maybe reference the UserAssignedIdentity from common-types?


Refers to: specification/eventgrid/resource-manager/Microsoft.EventGrid/preview/2025-04-15-preview/EventGrid.json:17813 in 9c8cf22. [](commit_id = 9c8cf22, deletion_comment = False)

@razvanbadea-msft
Copy link
Copy Markdown
Member

      "description": "Azure Active Directory Application ID or URI to get the access token that will be included as the bearer token in delivery requests.",

use the new name for AAD - Microsoft Entra Id in descriptions for clarity


Refers to: specification/eventgrid/resource-manager/Microsoft.EventGrid/preview/2025-04-15-preview/EventGrid.json:17842 in 9c8cf22. [](commit_id = 9c8cf22, deletion_comment = False)

@razvanbadea-msft
Copy link
Copy Markdown
Member

      "type": "string"

you can add uri format for these properties


Refers to: specification/eventgrid/resource-manager/Microsoft.EventGrid/preview/2025-04-15-preview/EventGrid.json:17839 in 9c8cf22. [](commit_id = 9c8cf22, deletion_comment = False)

@razvanbadea-msft
Copy link
Copy Markdown
Member

Fix the required checks which fails

@AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required NotReadyForARMReview and removed ARMChangesRequested labels Apr 22, 2025
@openapi-pipeline-app openapi-pipeline-app bot added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 22, 2025
@AzureRestAPISpecReview AzureRestAPISpecReview removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 22, 2025
@AzureRestAPISpecReview AzureRestAPISpecReview added WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required and removed BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required NotReadyForARMReview labels Apr 23, 2025
@bbi2015
Copy link
Copy Markdown
Member Author

bbi2015 commented Apr 23, 2025

Thanks for your feedback. We have other properties in swagger which represent base URL and we been using type: string for them.
Example:
Line 11971 -- "endpointBaseUrl": { "description": "The base URL that represents the endpoint of the partner destination.", "type": "string" },
Line 14054 -- "endpointBaseUrl": { "description": "The base URL that represents the endpoint of the destination of an event subscription.", "type": "string", "readOnly": true },
and others.
for sake of consistency, we would like to keep this one the same way.

Thanks for your feedback. We have other properties in swagger which represent base URL and we been using type: string for them.
Example:
Line 11971 -- "endpointBaseUrl": { "description": "The base URL that represents the endpoint of the partner destination.", "type": "string" },
Line 14054 -- "endpointBaseUrl": { "description": "The base URL that represents the endpoint of the destination of an event subscription.", "type": "string", "readOnly": true },
and others.
for sake of consistency, we would like to keep this one the same way.

You can keep type: string and add format: uri to indicate it's a URI. Will you be able to apply this to all similar properties?

Hi @gary-x-li ,

I have updated and PR and added format: uri to all new properties. I had tried adding format: uri to old properties as well, but seems like this fails the Breaking Change Test [Breaking Change Link]. Hence for now we would like to keep the existing ones as it is and incorporated your suggestions in the newly added properties.

The same behavior has been observed when I have added "format": "arm-id" and x-ms-arm-id-details to limit to identity resource type.

Copy link
Copy Markdown
Member

@a-hamad a-hamad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approved-Avocado Approved-Suppression ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. Event Grid new-api-version PublishToCustomers Acknowledgement the changes will be published to Azure customers. resource-manager SuppressionReviewRequired

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants